Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Author of the following commits did not sign a Contributor Agreement:
b39b076

Please, read and sign the above mentioned agreement if you want to contribute to this project

This PR is to address an issue I've run into when rendering the chart using HELM and deploying with Kubectl. The error message in Azure DevOps is:

• duplicated mapping key at line 40, column 31:

Upon closer examination, a fragment of the rendered stateful set looks like this:

template:
    metadata:
      name: "microk8s-master"
      labels:
        heritage: "Helm"
        release: "elk-es"
        chart: "elasticsearch"
        app: "microk8s-master"
        app: "microk8s-master"

The duplicate app key is caused by it's dual presence in the HELM template, which is being addressed by this PR

jenkins test this please

awesome, @jmlrt when do you think this will be available in the chart itself?

• If you're deploying the chart using master branch, it's already available.

• If you're using Helm repo, it will be available with next Elastic Stack release in a few weeks.

@jmlrt do you guys have an ETA for the next release? Didn't realize you guys were ok with having a broken chart in the registry for that long

@mmisztal1980 No ETA except that it will be released with the rest of Elastic Stack in a few weeks.

Note that the chart is working well with GKE and other tested k8s providers even with the duplicated label so we're not considering chart broken.